Dependency Updates #3242
Dependency Updates #3242
Conversation
|
/request-license-review |
License review requests: After all reviews have concluded, re-run the license-vetting check from the Github Actions web-interface to update its status. Workflow run (with attached summary files): |
eclipse-releng-bot
force-pushed
the
update_target
branch
from
d2cca21 to
097cb8c
Compare
|
Should we merge this? I'd like to keep Orbit in sync for the release so I will do the same for Orbit as what the Platform foes. |
|
I prefer to delay it for next release. |
|
Better safe than sorry seems a reasonable policy. |
eclipse-releng-bot
force-pushed
the
update_target
branch
2 times, most recently
from
fe39483 to
0de508b
Compare
|
FYI @msohn One concern I have with not picking up these changes is that EGit/JGit also uses sshd: 
Based on the Jetty 12.1.0 experience for M3, those updates may be applied for EGit/JGit such that SimRel ends up with the newer versions while the Platform ends up with the older versions. (I expect that SimRel will end up with only the largest version, which is a good thing.) But then of course it's impossible to keep Orbit in sync with both and when the Platform is used in any EPP product, it will be using the newer (untested) version. |
|
If there is someone to provide basic testing that e.g. ssh console still works we can try pushing it. |
|
FYI, I've updated Orbit anyway. The JAAS/ssh console is really not commonly exercised and appears not really to be tested outside of very long and tedious manual testing that I expect no one ever does. Orbit also updated jsoup; tips bundle that uses it in the Platform is not part of SimRel. |
eclipse-releng-bot
force-pushed
the
update_target
branch
19 times, most recently
from
d3e632f to
6bcb1e7
Compare
eclipse-releng-bot
force-pushed
the
update_target
branch
from
6bcb1e7 to
4b89406
Compare
akurtakov
force-pushed
the
update_target
branch
2 times, most recently
from
34c2aa9 to
7cc687a
Compare
eclipse-releng-bot
force-pushed
the
update_target
branch
8 times, most recently
from
62ca5b3 to
0d656ed
Compare
- org.mortbay.jasper:apache.*:.* is relocated to org.mortbay.jasper:mortbay-apache.*:.* - The BSN has also change org.mortbay.jasper.apache.* to org.mortbay.jasper.mortbay-apache.*. eclipse-platform#3242
- org.mortbay.jasper:apache.*:.* is relocated to org.mortbay.jasper:mortbay-apache.*:.* - The BSN has also change org.mortbay.jasper.apache.* to org.mortbay.jasper.mortbay-apache.*. - Keep old mortbay coordinates until uses to them have been removed via separate PRs. eclipse-platform#3242
- org.mortbay.jasper:apache.*:.* is relocated to org.mortbay.jasper:mortbay-apache.*:.* - The BSN has also change org.mortbay.jasper.apache.* to org.mortbay.jasper.mortbay-apache.*. - Keep old mortbay coordinates until uses to them have been removed via separate PRs. - Update exclude_list_external.txt with the new BSN. eclipse-platform#3242
eclipse-releng-bot
force-pushed
the
update_target
branch
2 times, most recently
from
bacacee to
9beb094
Compare
- org.mortbay.jasper:apache.*:.* is relocated to org.mortbay.jasper:mortbay-apache.*:.* - The BSN has also change org.mortbay.jasper.apache.* to org.mortbay.jasper.mortbay-apache.*. - Keep old mortbay coordinates until uses to them have been removed via separate PRs. - Update exclude_list_external.txt with the new BSN. #3242
eclipse-releng-bot
force-pushed
the
update_target
branch
3 times, most recently
from
e3e1173 to
0b72626
Compare
|
Oh dear, I forgot about this issue; I need to do the other changes in the other repositories now so we can delete the old coordinate. |
eclipse-releng-bot
force-pushed
the
update_target
branch
4 times, most recently
from
ed51b86 to
d2685d2
Compare
eclipse-releng-bot
force-pushed
the
update_target
branch
from
d2685d2 to
0f2bfeb
Compare
The content of the target
eclipse-sdk-prereqs.targetwas updatedPlease review the changes and merge if appropriate, or cherry pick individual updates.
The following maven artifacts have been updated:
org.apache.felix:org.apache.felix.scr:jar:2.2.12has been updated to version2.2.14